Skip to main content
TrustRadius
Redis™*

Redis™*

Overview

What is Redis™*?

Redis is an open source in-memory data structure server and NoSQL database.

Read more
Recent Reviews

TrustRadius Insights

Redis has proven itself to be an invaluable tool in a wide range of use cases. Users have found Redis to be exceptional as an efficient …
Continue reading

Set up & forget

7 out of 10
May 08, 2021
Incentivized
We use it to manage & control user sessions in a Tomcat based web application programmed with Java. It's used in both production and …
Continue reading

Redis Review

9 out of 10
February 03, 2020
Incentivized
Redis has been a vital component in our design, it's usage is mainly for caching API requests, but it also extends to other applications …
Continue reading

Redis is awesome!

9 out of 10
November 23, 2019
Incentivized
We're using Redis in many ways and across different departments in the organization. The most simple use case is to store locks so the …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 7 features
  • Performance (69)
    10.0
    100%
  • Scalability (69)
    9.4
    94%
  • Availability (69)
    9.0
    90%
  • Concurrency (68)
    9.0
    90%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Cloud

$388.00

On Premise
per month

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visithttps://redislabs.com/pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Features

NoSQL Databases

NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.

9.2
Avg 8.8
Return to navigation

Product Details

What is Redis™*?

According to the vendor, Redis is an in-memory multi-model database that supports multiple data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. Redis has built-in replication, Lua scripting, LRU eviction, transactions and different levels of on-disk persistence, and provides high availability and automatic partitioning with Redis Cluster.

Redis combines in-memory, schema-less design with optimized data structures and versatile modules that adapt to your data needs. The result is an adept, high performance, multi-purpose database that scales easily like a simple key/value data store but delivers sophisticated functionality with great simplicity, according to the vendor.

Redis also enables data persistence and high availability through replication and backups. Redis Enterprise is built from the ground up to serve as a system of record for any application.

*Redis is a trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd. Any use by TrustRadius is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Redis and TrustRadius.

Redis™* Features

NoSQL Databases Features

  • Supported: Performance
  • Supported: Availability
  • Supported: Concurrency
  • Supported: Security
  • Supported: Scalability
  • Supported: Data model flexibility
  • Supported: Deployment model flexibility

Additional Features

  • Supported: Integrated modules
  • Supported: Active-Passive Geo Distribution
  • Supported: Cluster Architecture
  • Supported: Linear Scaling
  • Supported: Durability
  • Supported: Backup and Disaster Recovery
  • Supported: Reliability

Redis™* Screenshots

Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of Screenshot of

Redis™* Video

Why Redis?

Redis™* Integrations

Redis™* Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac
Mobile ApplicationApple iOS, Android, Windows Phone, Blackberry, Mobile Web
Supported CountriesGlobal
Supported Languageshttps://redis.io/clients

Frequently Asked Questions

Redis is an open source in-memory data structure server and NoSQL database.

MongoDB, Amazon ElastiCache, and Couchbase Server are common alternatives for Redis™*.

Reviewers rate Performance highest, with a score of 10.

The most common users of Redis™* are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(224)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Redis has proven itself to be an invaluable tool in a wide range of use cases. Users have found Redis to be exceptional as an efficient caching solution, allowing for the distribution of data and storage of web sessions. This capability has led to significant improvements in performance and reliability, making it a go-to choice for many backend development teams. Additionally, Redis's versatility as a NoSQL key-based database store has made it a preferred option for organizations working alongside other databases like PostgreSQL and Memcache. Its ease of use, stability, and reliability have made it a popular choice across multiple departments within organizations.

Furthermore, Redis has been leveraged in various R&D projects to experiment with its implementation in different modules. Starting with cache management, users have been able to extend its usage to address specific project needs effectively. In these experiments, Redis has served as a traditional in-memory key store warehouse for cache systems with a vast number of items, resulting in substantial latency savings. Its ability to manage distributed queues efficiently has also made Redis an excellent choice for tasks that require multiple worker nodes to subscribe and complete tasks. The flexibility Redis offers by enabling users to store sets of object-based information and lists further improves performance through set operations.

In addition to these use cases, Redis has become synonymous with simplicity and speed when it comes to basic yet fast key-value storage solutions. It has been extensively adopted in organizations, including game studios, where it is used for storing user data, session data, game data, and indexing information. For example, Redis Enterprise has been utilized to support backend systems for casual games by providing sub-millisecond response times and facilitating clustering, sharding, backups, and monitoring.

Moreover, customers have found Redis instrumental in addressing various challenges such as big data processing, handling temporal data, managing session state, and even as a caching service in microservices environments. Its ability to provide data consistency, concurrency management, and high-speed operations has proven invaluable. Additionally, Redis has been a reliable tool for caching solutions in e-commerce storefronts and data visualization applications. Users have reported reduced server load and improved performance as a result of implementing Redis as a cache.

Redis has also found success as a buffer cache, allowing for faster data retrieval and improved overall database performance. Its role in processing queues, calling APIs, and supporting vital organizational workflows has been recognized by customers who rely on its stability and speed. Furthermore, users have implemented Redis across various domains to manage user timelines, build notification systems, and implement microservices architecture

Users recommend the following for Redis:

Consider other cache options before choosing Redis. It is advisable to try out other caching solutions before jumping to Redis, even though it is a great tool for highly distributed caching.

Understand the purpose of Redis in your implementation. It is important to have a clear understanding of how Redis will be used in your specific application. Don't assume that it will work straight out of the box. Evaluate data structures and choose a model that allows for faster query times.

Use Redis for specific use cases. Redis shines in certain areas such as synchronizing states across instances and handling user sessions with Node.js. It can also be a good alternative for relational data when speed is of utmost importance. However, users caution against abusing Redis and recommend using it in a reasonable way.

Overall, users believe that Redis is a valuable tool for fast reliable storage and caching, particularly for enterprise applications. However, they also advise considering other key-value stores depending on the specific use case at hand.

Attribute Ratings

Reviews

(1-7 of 7)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Redis is being leveraged to address big data, temporal data and session state challenges across the software stack. New opportunities to leverage it are continually being investigated and identified. It addresses data consistency and concurrency issues and provides amazing speed to what could be slower operations if handled without it.
  • Cache speed
  • Support for high volume of transactions with elegant handling of data sets
  • Ease of use - well structured and easy to implement
  • Price per shard is a bit high but over all there are no issues worth mentioning
  • I've heard some wishing it supported complex queries but this is asking the solution to support operations it wasn't intended for
Redis is well suited for:
  • Big data manipulation
  • Temporal data index structures
  • Distributed solutions
  • Publish/Subscribe model based solutions
Gene Baker | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We used Redis for application data caching. Redis is used by more than one department and is an enterprise standard offering. We have since moved away from Redis as we were able to simplify our architecture given our more powerful database servers after our latest tech refresh. When we were using Redis, our application response times were too slow for certain transactions so we cached the data to improve performance. There are other use cases that we considered like caching of session data. Again our goal was to simplify our architecture and Redis was one of the products we eliminated, not because it wasn't a good product but because we no longer needed it for our application.
  • Application data caching.
  • Session data caching.
  • Managing cache misses better.
I think Redis is a great product. Our problem was we were using too many different products when we could have been just using one. We had Redis for application data caching, we were using Xtreme Scale to cache session data, when in fact Redis could have handled both. The decision was made to stick with Xtreme Scale but honestly I would have preferred to stay with Redis. Redis handles application data caching well. We had some issues with cache misses, but I think that was more of what we did and less of what Redis did (or didn't do). That being said, after some recoding, we had no issues. I think that the Redis product could be little easier to use there but again, it was probably a learning curve item for us and not so much the product.
August 27, 2019

Reduced costs

Score 9 out of 10
Vetted Review
Verified User
Incentivized
Our development team uses it extensively.
  • Speeds up database searches.
  • Cloud-based without the need for on-prem.
  • High availability.
  • Support needs to be better, with chat support as an option.
  • Training material for new hire dev-ops.
  • Wiki-type documentation.
Redis is suited to database and back-end data processing.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
The R&D department uses Redis as 'in-memory' hot data storage (data storage layer of a machine learning big data architecture).
  • Low latency
  • Support hundreds of connections
  • Significant learning curve
  • Could be costly if not designed right
Good for big data storage architectures.
Less suitable if persistence is required.
June 25, 2019

Redis Review

Shehan Wickramarathne | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Redis to cache huge responses received from 3rd party services in our Backend to Frontend (BFF) layer, to improve performance and loading time in the frontend single page web application. It is used to cache pricing, product data which would stay fixed for a given amount of time. We were able to drastically reduce the loading time of pages in the frontend due to this caching mechanism using Redis.
  • Performance
  • Error resilient
  • Easy to use
  • Learning curve is steep
  • Developing in a local environment can be difficult.
Redis is well suited for quick caching and performance-centric applications.
December 13, 2018

Redis is goooood!!!

Rahul Chaudhary | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Redis is a basic, but extremely fast, key-value storage. We made a decision to use Redis because our use case didn't require a full blown database. We needed something to hold the data temporarily and loss of that data wouldn't lead to any issues. Redis was perfectly fitting our use case, and since then we are a bunch of happy Redis users.
  • Being a non-SQL database, it does not require any structure. Perfect for unstructured data like key-value pairs.
  • Redis is extremely fault tolerant. As soon as we write a record, it gets saved to the disk, without any performance issues.
  • Redis is very lightweight. In docker it takes less than 30MB, so it is so easy to run multiple containers in cluster without taking too much power.
  • Redis has a very good query API, and they are in their website each operation is clearly mentioned with its time complexity. This gives you a clear picture of performance. We didn't in fact do any performance testing because we trusted their site with all the information.
  • Redis has a very strong community around it. We have never found an issue for which a solution didn't exist beforehand.
  • A cluster in Redis was a little hard to understand and deploy, but this is a one time thing to learn, no worries.
Redis is extremely well suited for storing key-value kind of data. Flat and static values are around which they are built. There is no headache of indexing, or maintaining formats like other databases have.

I can also vouch for Redis's pub/sub notification. You can basically set expiration or event hooks around your keys, and Redis will trigger a notification for those events.

But Redis is ill-suited for treating it as a proper database. For instance, this is not a replacement for elasticsearch or mongo.

To assess if you need Redis, in my opinion, just think if you need to query values. If yes, don't use redis. If you are only concerned with key operations, then go with Redis.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
I used Redis in the context of an Airline company middleware implementation. At that time, we were looking for an efficient caching solution with the possibility to distribute data across nodes (i.e. sort of data grid without the complexity of a data grid).
Redis allowed us to build very fast a small cluster of nodes (4) serving as a cache for storing web sessions.
Because of additional features of Redis (pub/sub, in memory Keystore), Redis was also identified as non-critical storage for some data.
  • Redis is easy to learn and concepts are very simple. It's an in-memory storage with regular snapshots for data resiliency.
  • Redis offers the possibility to act as a cache with limited but strong eviction set policies. LRU is the most common one.
  • The pub/sub feature of Redis is an interesting alternative for efficient and fast data distribution when we don't need a central broker such as JMS. Obviously, it requires some analysis before choosing between the bunch of providers (JMS, Kafka, MQTT, AMQP, Redis, etc)
  • Redis is sponsored by Redislab which limit its functionalities. This is normal but they should push for a graphical tool for Redis monitoring. This tool is available for the enterprise edition, it would be nice to have a core version for the community
  • I don't know if Redis is available in containers, this might be interesting to have such capability
Redis fits perfectly when the cache is required or when fast data access is a criterion. With the community edition, we can build very fast and efficient cluster of data nodes with adequate persistent policy.

I don't recommend Redis if you are looking for something else than a key/value store. Even if Redis claims to be a "data structure server", you might face limitations while dealing with other data structures.
Return to navigation